Controlling access to a vault server in a multitenant environment

ABSTRACT

A computer-implemented method includes: receiving, by a computing device, a vault access request for vault credentials stored by a vault server; verifying, by the computing device, whether a source of the vault access request originated from a multitenant application server; preventing, by the computing device, access to the vault server and the vault credentials when the source of the vault access request has not been verified as originating from the multitenant application server; obtaining, by the computing device, vault credentials from a vault server based on verifying that the source of the vault access request originated from the multitenant application server; and executing, by the computing device, a multitenant application task using the vault credentials.

BACKGROUND

The present invention generally relates to controlling access to a vaultserver and, more particularly, to controlling access to a vault serverresiding on a client network outside of a service provider network in amultitenant environment.

Software multitenancy is a software architecture in which a singleinstance of software runs on a server and serves multiple tenants. Atenant is a group of users who share a common access with specificprivileges to the software instance. With a multitenant architecture, asoftware application (e.g., a multitenant application) is designed toprovide every tenant a dedicated share of the instance—including itsdata, configuration, user management, tenant individual functionalityand non-functional properties.

SUMMARY

In an aspect of the invention, a computer-implemented method includes:receiving, by a computing device, a vault access request for vaultcredentials stored by a vault server; verifying, by the computingdevice, whether a source of the vault access request originated from amultitenant application server; preventing, by the computing device,access to the vault server and the vault credentials when the source ofthe vault access request has not been verified as originating from themultitenant application server; obtaining, by the computing device,vault credentials from a vault server based on verifying that the sourceof the vault access request originated from the multitenant applicationserver; and executing, by the computing device, a multitenantapplication task using the vault credentials.

In an aspect of the invention, there is a computer program product forcontrolling access to a vault server and vault credentials stored by thevault server. The computer program product comprises a computer readablestorage medium having program instructions embodied therewith, theprogram instructions executable by a computing device to cause thecomputing device to: receive a vault access request for the vaultcredentials stored by the vault server; verify whether a source of thevault access request originated from a multitenant application server;prevent access to the vault server and the vault credentials when thesource of the vault access request has not been verified as originatingfrom the multitenant application server; and obtain vault credentialsfrom a vault server and provide the vault credentials to the multitenantapplication server based on verifying that the source of the vaultaccess request originated from the multitenant application server.

In an aspect of the invention a system comprises: a CPU, a computerreadable memory and a computer readable storage medium associated with acomputing device; program instructions to receive an applicationinstruction and a vault access request for vault credentials stored by avault server; program instructions to determine that the vault accessrequest was received from a multitenant application server; programinstructions to obtain vault credentials from a vault server based ondetermining that the vault access request was received from themultitenant application server; and program instructions to execute amultitenant application task using the vault credentials in accordancewith the application instruction. Executing the multitenant applicationtask includes accessing one or more client devices using the vaultcredentials. The program instructions are stored on the computerreadable storage medium for execution by the CPU via the computerreadable memory.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in the detailed description whichfollows, in reference to the noted plurality of drawings by way ofnon-limiting examples of exemplary embodiments of the present invention.

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 shows an overview of an example implementation in accordance withaspects of the present invention.

FIG. 5 shows an example flowchart for verifying the source of a vaultaccess request in accordance with aspects of the present invention.

FIG. 6 shows an example flowchart for executing a multitenantapplication task after processing a vault access request originatingfrom a multitenant application server in accordance with aspects of thepresent invention.

DETAILED DESCRIPTION

The present invention generally relates to controlling access to a vaultserver and, more particularly, to controlling access to a vault serverresiding on a client network outside of a service provider network in amultitenant environment. As described herein, a multitenant applicationserver residing within a service provider network may access a vaultserver residing within a client network. For example, the multitenantapplication server may access the vault server to receive credentialsused to access a client server (e.g., to perform a task on the clientserver, such as remediating an error using a virtual engineer).Additionally, or alternatively, the multitenant application server mayaccess the vault server for another purpose (e.g., to manage filesstored by the file fault server). The multitenant application server mayrequest access to the vault via a jump host server residing in theclient network. For example, the multitenant application server mayprovide credentials (e.g., user identifier, password, script, hashvalue, execution location information, etc.) to the jump host server,and the jump host server may provide access to the vault server uponverification of the credentials. Since the vault resides on the clientnetwork and is outside of the service provider network, a user withinthe client network (e.g., a “root user,” a “super user,” a “superadministrator”, etc.) may access the vault server. Aspects of thepresent invention may reduce or eliminate a security risk in whichunauthorized users within the client network may access the vault. Forexample, accessing the vault server by an entity other than themultitenant application server may pose a security risk and/or maycomprise the functionality of a multitenant application hosted by themultitenant application server.

Aspects of the present invention provide a security module that verifiesthat a request to access a vault server originates from a multitenantapplication server (e.g., as opposed to from another source, such as aroot user). As a result, the vault server may only be accessed by themultitenant application server and protected from being accessed by auser or other entity. Advantageously, security of the vault server andits contents may be improved.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a nonremovable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;

transaction processing 95; and vault access request source verification96.

Referring back to FIG. 1, the program/utility 40 may include one or moreprogram modules 42 that generally carry out the functions and/ormethodologies of embodiments of the invention as described herein (e.g.,such as the functionality provided by vault access request sourceverification 96). Specifically, the program modules 42 may receive avault access request, verify the source of the vault access request, andobtain vault credentials stored by a vault server based on verifyingthat the vault access request originated from a multitenant applicationserver. Other functionalities of the program modules 42 are describedfurther herein such that the program modules 42 are not limited to thefunctions described above. Moreover, it is noted that some of themodules 42 can be implemented within the infrastructure shown in FIGS.1-3. For example, the modules 42 may be representative of a jump hostserver as shown in FIG. 4.

FIG. 4 shows an overview of an example implementation in accordance withaspects of the present invention. As shown in FIG. 4, environment 200may include a service provider network 202 and a client network 204. Theservice provider network 202 may include a multitenant applicationserver 210. The client network 204 may include a jump host server 215, avault server 225, and client servers 230.

The multitenant application server 210 may include one or more serverdevices that implement a multitenant application. In embodiments, themultitenant application server 210 may include one or more components ofthe computer system/server 12 of FIG. 1.

The jump host server 215 may include one or more server devices thatprovide the multitenant application server 210 with access to the vaultserver 225. In embodiments, the jump host server 215 may include one ormore components of the computer system/server 12 of FIG. 1. The jumphost server 215 may include a vault security module 220 that verifies asource of a request to access the vault server 225. The vault securitymodule 220 may include one more program modules 42 of FIG. 1.

The vault server 225 may include one or more server devices that storefiles that may be accessed by the multitenant application server 210.For example, the vault server 225 may store credentials that themultitenant application server 210 may use to access client serverswithin the client network 204 (as described in greater detail below withrespect to FIG. 5). In embodiments, the vault server 225 may include oneor more components of the computer system/server 12 of FIG. 1.

The client servers 230 may include one or more server devices thatimplement services or applications within the client network 204. Inembodiments, the client servers 230 may include one or more componentsof the computer system/server 12 of FIG. 1. Access to client servers 230may be protected by credentials stored by the vault server 225.

In embodiments, the service provider network 202 and the client network204 may communicate via an intermediate network which may include one ormore wired and/or wireless networks. For example, the intermediatenetwork may include a cellular network (e.g., a second generation (2G)network, a third generation (3G) network, a fourth generation (4G)network, a fifth generation (5G) network, a long-term evolution (LTE)network, a global system for mobile (GSM) network, a code divisionmultiple access (CDMA) network, an evolution-data optimized (EVDO)network, or the like), a public land mobile network (PLMN), and/oranother network. Additionally, or alternatively, the intermediatenetwork may include a local area network (LAN), a wide area network(WAN), a metropolitan network (MAN), the Public Switched TelephoneNetwork (PSTN), an ad hoc network, a managed Internet Protocol (IP)network, a virtual private network (VPN), an intranet, the Internet, afiber optic-based network, and/or a combination of these or other typesof networks.

As shown in FIG. 4, at step 2.1, the multitenant application server 210may provide an application instruction to the jump host server 215. Forexample, the application instruction may include instructions relatingto the execution of a multitenant application task in which clientservers 230 are accessed to remediate an error. Additionally, oralternatively, the application instruction may relate to another type ofapplication. As described herein, access to client servers 230 may beneeded in order to execute the application instructions. Access to theclient servers 230 may be protected by vault credentials stored by thevault server 225. Accordingly, the application instructions may includea request to access the vault (e.g., so that vault credentials stored bythe vault may be used to access the client servers 230 and, in turn,execute the application instructions). In embodiments, the vault accessrequest may include credentials and authentication information for themultitenant application server 210 (e.g., a certificate and/or othertype of authentication information). In embodiments, the applicationinstructions and the vault access request may be provided via a securechannel or tunnel.

The jump host server 215 may receive the application instruction and thevault access request. At step 2.2, the jump host server 215 may verifythe credentials included in the vault access request (e.g., to verifythat the multitenant application server 210 is authorized to request thevault credentials). As described herein, the credentials included in thevault access request are different than the vault credentials stored bythe vault server 225. More specifically, the credentials included in thevault access request may be used to verify that a request to access thevault credentials is received from an authorized party (e.g., anauthorized multitenant application server 210).

At step 2.3 (e.g., after verifying the credentials of the vault accessrequest), the vault access request is provided to the vault securitymodule 220. At step 2.4, the vault security module 220 may verify theidentity of the source of the vault access request. More specifically,the vault security module 220 may use the certificate included in thevault access request to verify that source of the vault access requestis from the multitenant application server 210 (e.g., using acertificate-based authentication technique). Additionally, oralternatively, the vault security module 220 may use any otherauthentication technique, or combination thereof, to verify the identityof the source of the vault access request (e.g., hash value matching,encryption and decryption techniques, or the like). Additionally, oralternatively, the vault security module 220 may verify the identity ofthe source of the vault access request based on an internet protocol(IP) address from which the vault access request was received.Additionally, or alternatively, the vault security module 220 may verifythe identity of the source of the vault access request based on a typeof security protocol via which the vault access request was received.

At step 2.5, the vault security module 220 may provide unlockcredentials to the vault server 225 to access the vault server 225(e.g., based on verifying that the identity of the source of the vaultaccess request is the multitenant application server 210). In otherwords, the vault security module 220 may provide unlock credentials tothe vault server 225 based on verifying that the vault access requestwas received from the multitenant application server 210, and not fromanother source (e.g., a root user or super user that may request accessto the vault server 225 via a vault access API). In this way, the vaultserver 225 cannot be accessed by a root user, as the source of the vaultrequest must come from the multitenant application server 210.

As described herein, the unlock credentials may include a set ofcredentials that may be different than the credentials of the vaultaccess request. Additionally, or alternatively, the unlock credentialsmay include a hash value, a script, user ID, execution locationinformation, or the like. At step 2.6, the vault server 225 may verifythe unlock credentials and may also authenticate the vault securitymodule 220 to verify that the unlock credentials originated from thevault security module 220 (e.g., using hash value verification and/orother techniques). At step 2.7, the vault server 225 may provide thevault credentials stored by the vault server 225 to the vault securitymodule 220. At step 2.8, the vault security module 220 may provide thevault credentials to the jump host server 215. At step 2.9, the jumphost server 215 may execute the application instruction using the vaultcredentials. For example, the jump host server 215 may use the vaultcredentials to access the client servers 230 as part of the applicationexecution. As an illustrative, non-limiting example, the jump hostserver 215 may execute an application to remediate a problem on theclient servers 230. Accordingly, the jump host server 215 may use thevault credentials to access the client servers 230 in order to remediatethe problem in accordance with the application instructions.Alternatively, the jump host server 215 may use the vault credentials toaccess the client servers 230 in order to perform another task inaccordance with the application instructions.

At step 2.10, the jump host server 215 may provide the vault credentialsto the multitenant application server 210. The multitenant applicationserver 210 may store the vault credentials for future use. For example,at step 2.11, the multitenant application server 210 may provide anapplication instruction (e.g., via a secure channel) to the jump hostserver 215 in which the application instruction includes the vaultcredentials. Based on receiving the vault credentials, the jump hostserver 215 may execute the application using the vault credentials(e.g., in a similar manner as discussed above with respect to step 2.9).

The quantity of devices and/or networks in the environment 200 is notlimited to what is shown in FIG. 4. In practice, the environment 200 mayinclude additional devices and/or networks; fewer devices and/ornetworks; different devices and/or networks; or differently arrangeddevices and/or networks than illustrated in FIG. 4. Also, in someimplementations, one or more of the devices of the environment 200 mayperform one or more functions described as being performed by anotherone or more of the devices of the environment 200. Devices of theenvironment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

FIG. 5 shows an example flowchart for verifying the source of a vaultaccess request in accordance with aspects of the present invention. Thesteps of FIG. 5 may be implemented in the environment of FIG. 4, forexample, and are described using reference numbers of elements depictedin FIG. 4. As noted above, the flowchart illustrates the architecture,functionality, and operation of possible implementations of systems,methods, and computer program products according to various embodimentsof the present invention.

As shown in FIG. 5, process 500 may include receiving an applicationinstruction with a vault access request for vault credentials (step510). For example, the jump host server 215 may receive an applicationinstruction with a vault access request for vault credentials stored bythe vault server 225 (e.g., in a similar manner as described above withrespect to step 2.1 of FIG. 4). In embodiments, a multitenantapplication server 210 may provide the application instruction. Theapplication instruction may include a request for the jump host server215 to execute a multitenant application task within the client network204 and by communicating with particular client servers 230 as requiredby the multitenant application. The multitenant application server 210may also provide the vault access request if the multitenant applicationserver 210 is not currently storing vault credentials used to accessclient devices 230 that may need to be accessed in connection withexecution of the application instruction. As described herein, the vaultaccess request may include a set of credentials, a certificate, and/orother information that may be verified in order to process the vaultaccess request.

Process 500 may also include verifying credentials included in the vaultaccess request (step 520). For example, the jump host server 215 mayverify the credentials included in the vault access request (e.g., in asimilar manner as described above with respect to step 2.2 of FIG. 4).

Process 500 may further include verifying the source of the vault accessrequest as originating from a multitenant application server (step 530).For example, the vault security module 220 of the jump host server 215may verify the source of the vault access request as originating fromthe multitenant application server 210 (e.g., in a similar manner asdescribed above with respect to step 2.4 of FIG. 4). More specifically,the vault security module 220 may use the certificate included in thevault access request to verify that the vault access request wasreceived from the multitenant application server 210 (e.g., using acertificate-based authentication technique). Additionally, oralternatively, the vault security module 220 may use any otherauthentication technique, or combination thereof, to verify the identityof the source of the vault access request (e.g., hash value matching,encryption and decryption techniques, or the like). Additionally, oralternatively, the vault security module 220 may verify the identity ofthe source of the vault access request based on an internet protocol(IP) address from which the vault access request was received.Additionally, or alternatively, the vault security module 220 may verifythe identity of the source of the vault access request based on.

As described herein, the vault security module 220 may verify that thevault access request was received from the multitenant applicationserver 210, and not from another source (e.g., a root user or super userthat may request access to the vault server 225 via a vault access API).In this way, the vault server 225 cannot be accessed by a root user, asthe source of the vault request must come from the multitenantapplication server 210. For example, if, at step 540, the source of thevault access request has not been verified as the multitenantapplication server 210, process 500 may include preventing access to thevault server 225 (step 550). In embodiments, the vault security module220 may prevent access to the vault server 225 and may not provide theunlocked credentials if the source of the vault access request has notbeen verified as the multitenant application server 210, or if the vaultaccess request has been determined to have originated from a sourceother than the multitenant application server 210. In embodiments, thevault security module 220 may discard the request and/or provide analert to an administer device indicating an attempt to access the vaultserver 225 by a source other than the multitenant application server210.

If, at step 540, the source of the vault access request has beenverified as the multitenant application server 210, process 500 may alsoinclude obtaining vault credentials from a vault server based onverifying the source of the vault access request (step 560). Forexample, the vault security module 220 of the jump host server 215 mayobtain the vault credentials by providing unlocked credentials to thevault server 225 based on verifying the source of the vault accessrequest (e.g., in a similar manner as described above with respect tostep 2.5 of FIG. 4). More specifically, the vault security module 220may provide the unlock credentials based on verifying that the vaultaccess request originated from the multitenant application server 210.The vault server 225 may receive verify the unlock credentials and mayalso authenticate the vault security module 220 to verify that theunlock credentials originated from the vault security module 220 (e.g.,as described above with respect to step 2.6 of FIG. 4). Further, thevault server 225 may provide the vault credentials to the vault securitymodule 220, and the vault security module 220 may receive the vaultcredentials stored by the vault server 225 (e.g., in a similar manner asdescribed above with respect to step 2.7 of FIG. 4). In embodiments, thevault security module 220 may provide the vault credentials to anothercomponent of the jump host server 215 (e.g., an application executioncomponent, or the like).

Process 500 may further include executing a multitenant application taskusing the vault credentials (step 570). For example, the jump hostserver 215 may execute the multitenant application task (e.g., inaccordance with the application instruction of step 510) using the vaultcredentials (e.g., by accessing the client servers 230 as required bythe execution of the multitenant application).

Process 500 may also include providing the vault credentials to themultitenant application server (block 580). For example, the jump hostserver 215 may provide the vault credentials to the multitenantapplication server 210 (e.g., in a similar manner as described abovewith respect to step 2.10). Based on receiving the vault credentials,the multitenant application server 210 may store the vault credentialsfor future use, as described herein.

FIG. 6 shows an example flowchart for executing a multitenantapplication after processing a vault access requested originating from amultitenant application server in accordance with aspects of the presentinvention. The steps of FIG. 6 may be implemented in the environment ofFIG. 4, for example, and are described using reference numbers ofelements depicted in FIG. 4. As noted above, the flowchart illustratesthe architecture, functionality, and operation of possibleimplementations of systems, methods, and computer program productsaccording to various embodiments of the present invention.

As shown in FIG. 6, process 600 may include receiving an applicationinstruction with vault credentials (block 610). For example, the jumphost server 215 may receive an application instruction with vaultcredentials from the multitenant application server 210 (e.g., in asimilar manner as described above with respect to step 2.11). Asdescribed herein, the application instruction may include a request forthe jump host server 215 to execute a multitenant application within theclient network 204 and by communicating with particular client servers230 as required. As described herein, multitenant application server 210may provide vault credentials used to access the client servers 230 inconnection with executing the multitenant application task when themultitenant application server 210 previously receives the vaultcredentials from the jump host server 215 (e.g., as described withrespect to step 2.10 of FIG. 4 and step 550 of FIG. 5).

Process 600 may further include authenticating the applicationinstruction (step 620). For example, the jump host server 215 mayauthenticate the application instruction to verify that the applicationinstruction originated from the multitenant application server 210. Inembodiments, the jump host server 215 may authenticate the applicationinstruction using one or more authentication techniques. Process 600 mayalso include executing the multitenant application task using the vaultcredentials (step 630). For example, the jump host server 215 mayexecute the multitenant application task in accordance with theapplication instruction (e.g., by accessing the client servers 230 usingthe vault credentials as required by the execution of the multitenantapplication task). In this way, the multitenant application server 210may direct jump host server 215 to execute a multitenant applicationtask without the need to access the vault server 225, as multitenantapplication server 210 has previously received and stored the vaultcredentials (e.g., as described above with respect to the process ofFIG. 5). That is, the multitenant application server 210 may direct jumphost server 215 to execute a multitenant application task withoutadditional involvement from the vault server 225.

In embodiments, a service provider, such as a Solution Integrator, couldoffer to perform the processes described herein. In this case, theservice provider can create, maintain, deploy, support, etc., thecomputer infrastructure that performs the process steps of the inventionfor one or more customers. These customers may be, for example, anybusiness that uses technology. In return, the service provider canreceive payment from the customer(s) under a subscription and/or feeagreement and/or the service provider can receive payment from the saleof advertising content to one or more third parties.

In still additional embodiments, the invention provides acomputer-implemented method, via a network. In this case, a computerinfrastructure, such as computer system/server 12 (FIG. 1), can beprovided and one or more systems for performing the processes of theinvention can be obtained (e.g., created, purchased, used, modified,etc.) and deployed to the computer infrastructure. To this extent, thedeployment of a system can comprise one or more of: (1) installingprogram code on a computing device, such as computer system/server 12(as shown in FIG. 1), from a computer-readable medium; (2) adding one ormore computing devices to the computer infrastructure; and (3)incorporating and/or modifying one or more existing systems of thecomputer infrastructure to enable the computer infrastructure to performthe processes of the invention.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A computer-implemented method comprising:receiving, by a computing device implemented in a client network, avault access request for vault credentials stored by a vault serverimplemented in the client network; verifying, by the computing device,that a source of the vault access request originated from a multitenantapplication server which is implemented in a service provider networkseparate from the client network; obtaining, by the computing device,vault credentials from the vault server based on verifying that thesource of the vault access request originated from the multitenantapplication server; and storing, at the multitenant application server,the vault credentials obtained from the vault server, the multitenantapplication server uses the vault credentials to execute a multitenantapplication task without having to access the vault server.
 2. Themethod of claim 1, wherein the vault credentials are required to accessone or more client servers in the client network.
 3. The method of claim1, wherein the verifying whether the source of the vault access requestoriginated from a multitenant application server is performed by a vaultsecurity module implemented within the computing device.
 4. The methodof claim 1, further comprising verifying, by the computing device, thatthe vault access request includes credentials that a party requestingthe vault credentials is an authorized party.
 5. The method of claim 1,wherein the vault access request includes authentication informationused to verify the source of the vault access request.
 6. The method ofclaim 5, wherein: the authentication information includes a certificate,and the verifying whether the source of the vault access requestoriginated from a multitenant application server is based on at leastone of: certificate-based authentication; hash value matching;encryption or decryption; an internet protocol (IP) address via whichthe vault access request is received; and a type of security protocolvia which the vault access request is received.
 7. The method of claim1, further comprising preventing, by the computing device, access to thevault server and the vault credentials when the source of the vaultaccess request has not been verified as originating from the multitenantapplication server.
 8. The method of claim 1, further comprisingreceiving an application instruction as part of the vault accessrequest.
 9. The method of claim 8, further comprising executing themultitenant application task by executing the multitenant applicationtask in accordance with the application instruction.
 10. The method ofclaim 9, wherein executing the multitenant application task includesaccessing one or more client servers using the vault credentials. 11.The method of claim 10, further comprising providing the vaultcredentials to the multitenant application server.
 12. The method ofclaim 11, further comprising: receiving an application instructionincluding the vault credentials from the multitenant application serverafter executing the multitenant application task; and executing anadditional multitenant application task using the vault credentialsincluded in the application instruction.
 13. The method of claim 12,wherein the additional multitenant application task is executed withoutadditional involvement of the vault server.
 14. The method of claim 1,wherein the computing device is implemented within a client network andthe multitenant application server is implemented with a serviceprovider network, wherein the client network and the service providernetwork are separate networks.
 15. The method of claim 1, furthercomprising deploying a system for controlling access to the vault serverand the vault credentials, comprising providing a computerinfrastructure operable to perform the steps of claim
 1. 16. A computerprogram product for controlling access to a vault server implemented ina client network, including one or more client servers, and vaultcredentials stored by the vault server, the computer program productcomprising a computer readable storage medium having programinstructions embodied therewith, the program instructions executable bya computing device to cause the computing device to: receive, by a jumphost server in the client network, a vault access request for the vaultcredentials stored by the vault server, the vault credentials beingrequired to access the one or more client servers in the client network;verify, by the jump host server, whether a source of the vault accessrequest originated from a multitenant application server which iscoupled to the jump host server and which is implemented in a serviceprovider network which is separate from the client network; obtain vaultcredentials from the vault server, by the jump host server, and providethe vault credentials, by the jump host server, to the multitenantapplication server based on verifying that the source of the vaultaccess request originated from the multitenant application server toallow the multitenant application server to access the one or moreclient servers; and store, at the multitenant application server, thevault credentials obtained from the vault server, wherein themultitenant application server uses the vault credentials to execute amultitenant application task without having to access the vault server.17. The computer program product of claim 16, wherein verifying whethera source of the vault access request originated from a multitenantapplication server is performed by a vault security module implementedwithin the computing device.
 18. The computer program product of claim16, wherein the program instructions further cause the computing deviceto execute a multitenant application task using the vault credentials inaccordance with an application instruction received from the multitenantapplication server.
 19. A system comprising: a CPU, a computer readablememory and a computer readable storage medium associated with acomputing device; program instructions to receive an applicationinstruction and a vault access request for vault credentials stored by avault server; program instructions to verify by a jump host server,connected to the vault server, a multitenant application server andclient servers, that the vault access request includes credentials thata party requesting the vault credentials is an authorized party; programinstructions to obtain the vault credentials from the vault server basedon determining that the vault access request was received from themultitenant application server; program instructions to execute amultitenant application task using the vault credentials in accordancewith the application instruction; and program instructions to store, atthe multitenant application server, the vault credentials obtained fromthe vault server, wherein the multitenant application server uses thevault credentials to execute a multitenant application task withouthaving to access the vault server.
 20. The system of claim 19, furthercomprising program instructions to determine that the vault accessrequest was received from the multitenant application based on at leastone of: certificate-based authentication; hash value matching;encryption or decryption; an internet protocol (IP) address via whichthe vault access request is received; and a type of security protocolvia which the vault access request is received.